Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 44ff5a438bbf4a0adf23c40814d1b8f7313c91f73764df38156649e9d67705e2

Tx prefix hash: a076d15650a641c960a695687680c4593e2cace864dc987f67ec4116e34f9d90
Tx public key: 37d8f8648fd9c4a8af5cead18afacafda94841a785f0be76442bc01c42d85abe
Timestamp: 1578548259 Timestamp [UCT]: 2020-01-09 05:37:39 Age [y:d:h:m:s]: 05:056:04:11:10
Block: 41796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1190075 RingCT/type: yes/0
Extra: 0137d8f8648fd9c4a8af5cead18afacafda94841a785f0be76442bc01c42d85abe02110000005649b77a3d000000000000000000

1 output(s) for total of 446.183336394000 dcy

stealth address amount amount idx
00: 400f49d2c5168644916b59564ad6b797f62a53df3fe758864f4b040d8ac9b3dc 446.183336394000 74848 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 41806, "vin": [ { "gen": { "height": 41796 } } ], "vout": [ { "amount": 446183336394, "target": { "key": "400f49d2c5168644916b59564ad6b797f62a53df3fe758864f4b040d8ac9b3dc" } } ], "extra": [ 1, 55, 216, 248, 100, 143, 217, 196, 168, 175, 92, 234, 209, 138, 250, 202, 253, 169, 72, 65, 167, 133, 240, 190, 118, 68, 43, 192, 28, 66, 216, 90, 190, 2, 17, 0, 0, 0, 86, 73, 183, 122, 61, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8