Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b078ac001804992db0eaa4e575adb5e7c125f168d373f907184d45f3ade49e95

Tx prefix hash: 369537272eac348c1012f4d310fe71f9fa016615cd9aa85d7fcb73ca26f3b88e
Tx public key: 3d0c52f7f7d067e1c2ef4c7be563782cc7571b25cec9598c52a00151ec7dd457
Timestamp: 1732059513 Timestamp [UCT]: 2024-11-19 23:38:33 Age [y:d:h:m:s]: 01:013:14:52:11
Block: 1157446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268182 RingCT/type: yes/0
Extra: 013d0c52f7f7d067e1c2ef4c7be563782cc7571b25cec9598c52a00151ec7dd457021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0937c18d4c0453f05381df7d85ce06e62b594cd683729090d413d87f9aa8c6a8 0.600000000000 1643069 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": 1157456, "vin": [ { "gen": { "height": 1157446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0937c18d4c0453f05381df7d85ce06e62b594cd683729090d413d87f9aa8c6a8" } } ], "extra": [ 1, 61, 12, 82, 247, 247, 208, 103, 225, 194, 239, 76, 123, 229, 99, 120, 44, 199, 87, 27, 37, 206, 201, 89, 140, 82, 160, 1, 81, 236, 125, 212, 87, 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