Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd578ab78338669071622f248088fc91f973d36c78b269b26857f4a3067769bc

Tx prefix hash: 09baf1907a3166cffa9a5bdf1a4ecdde84d389faa348d850dbca6a7fbf66fd23
Tx public key: 852d498bbb1cb8d0dcdae6febecc223337bb7d3e3d6262b926199cdc7499b2b2
Timestamp: 1731590105 Timestamp [UCT]: 2024-11-14 13:15:05 Age [y:d:h:m:s]: 00:138:17:01:16
Block: 1153548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98947 RingCT/type: yes/0
Extra: 01852d498bbb1cb8d0dcdae6febecc223337bb7d3e3d6262b926199cdc7499b2b2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d29e311f86da3354c52d0880acb3562fbef3eae90ed84d3fda7a6cdbe2b0b58e 0.600000000000 1639157 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": 1153558, "vin": [ { "gen": { "height": 1153548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d29e311f86da3354c52d0880acb3562fbef3eae90ed84d3fda7a6cdbe2b0b58e" } } ], "extra": [ 1, 133, 45, 73, 139, 187, 28, 184, 208, 220, 218, 230, 254, 190, 204, 34, 51, 55, 187, 125, 62, 61, 98, 98, 185, 38, 25, 156, 220, 116, 153, 178, 178, 2, 17, 0, 0, 0, 3, 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