Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c51647874b86c97e2a0539df58c72049a25511cafb103ed49f1d05f94c9e79b

Tx prefix hash: 5c9b11a56600470dee2d90ad0e979ac78c871a1471b7844d313d8833ac17f790
Tx public key: 1b32900b7db90fe89f6feafebd867845f45715b01b91a02b17e7e6d41f04f2d3
Timestamp: 1735972237 Timestamp [UCT]: 2025-01-04 06:30:37 Age [y:d:h:m:s]: 00:165:10:22:47
Block: 1189854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117929 RingCT/type: yes/0
Extra: 011b32900b7db90fe89f6feafebd867845f45715b01b91a02b17e7e6d41f04f2d302110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6904b9239ab1652019a7dfeb21ccfd716984a9a4e89b564fcb2603217d7c0bb 0.600000000000 1676367 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": 1189864, "vin": [ { "gen": { "height": 1189854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6904b9239ab1652019a7dfeb21ccfd716984a9a4e89b564fcb2603217d7c0bb" } } ], "extra": [ 1, 27, 50, 144, 11, 125, 185, 15, 232, 159, 111, 234, 254, 189, 134, 120, 69, 244, 87, 21, 176, 27, 145, 160, 43, 23, 231, 230, 212, 31, 4, 242, 211, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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