Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c62d86f26ce1b6ace20417bf641f1220d8c06c578386ca4f83dc07fdeb71ec6e

Tx prefix hash: 87b421ead3c262cd0621be1bdc8ad6bf7e3a690cde6ce962746b7dae0d73c7bc
Tx public key: d40bde1360aa5d8946c6918a1346e77308d45550147012c283ed45f8e68ca30c
Timestamp: 1731383295 Timestamp [UCT]: 2024-11-12 03:48:15 Age [y:d:h:m:s]: 00:139:18:37:09
Block: 1151831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99726 RingCT/type: yes/0
Extra: 01d40bde1360aa5d8946c6918a1346e77308d45550147012c283ed45f8e68ca30c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 621366fc6fb3d14f75e2c0cc0ea9967899e8c37eea0a7ae6050773e038f51e70 0.600000000000 1637414 of 15

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": 1151841, "vin": [ { "gen": { "height": 1151831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "621366fc6fb3d14f75e2c0cc0ea9967899e8c37eea0a7ae6050773e038f51e70" } } ], "extra": [ 1, 212, 11, 222, 19, 96, 170, 93, 137, 70, 198, 145, 138, 19, 70, 231, 115, 8, 212, 85, 80, 20, 112, 18, 194, 131, 237, 69, 248, 230, 140, 163, 12, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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