Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ea56df50786690985475bedca5ac054534a0b7d556d2ff0aeb444e242c45ecb

Tx prefix hash: b20c71d19a3133c4b6b2ba2e996993fdc32a11db0474e2bbe35e3ab0c226c6d9
Tx public key: ab799505ea5d59a9ab3046f7c64186fbccd50dc0c3fa4264d5a38b2b13093714
Timestamp: 1582051598 Timestamp [UCT]: 2020-02-18 18:46:38 Age [y:d:h:m:s]: 04:283:03:38:14
Block: 67697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1094716 RingCT/type: yes/0
Extra: 01ab799505ea5d59a9ab3046f7c64186fbccd50dc0c3fa4264d5a38b2b1309371402110000001ad81c26c0000000000000000000

1 output(s) for total of 366.178249056000 dcy

stealth address amount amount idx
00: 6cb162b5c5ad3a310a3608e51408fd771fe3fb48fe6082276b5d39ef8f4c91f0 366.178249056000 124676 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": 67707, "vin": [ { "gen": { "height": 67697 } } ], "vout": [ { "amount": 366178249056, "target": { "key": "6cb162b5c5ad3a310a3608e51408fd771fe3fb48fe6082276b5d39ef8f4c91f0" } } ], "extra": [ 1, 171, 121, 149, 5, 234, 93, 89, 169, 171, 48, 70, 247, 198, 65, 134, 251, 204, 213, 13, 192, 195, 250, 66, 100, 213, 163, 139, 43, 19, 9, 55, 20, 2, 17, 0, 0, 0, 26, 216, 28, 38, 192, 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