Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51712dc77c3c30d32d271f708cbf7301cc82ea7a6dad9cc4e4ad69601db0d9ca

Tx prefix hash: 867dd9af7a659083cc828bacdd3e9a91db508f20be835af098c8b4ba048aa1b8
Tx public key: 9c5fceaae5102c37020252932e948759784bc0f5b3d065d3a32a4205f09b056d
Timestamp: 1740182032 Timestamp [UCT]: 2025-02-21 23:53:52 Age [y:d:h:m:s]: 00:273:01:28:45
Block: 1224405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192932 RingCT/type: yes/0
Extra: 019c5fceaae5102c37020252932e948759784bc0f5b3d065d3a32a4205f09b056d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c769fab62d439c47b79b764c3ea01f6f64d2b3339b30b3368abc1aec0c640cd 0.600000000000 1711264 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": 1224415, "vin": [ { "gen": { "height": 1224405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c769fab62d439c47b79b764c3ea01f6f64d2b3339b30b3368abc1aec0c640cd" } } ], "extra": [ 1, 156, 95, 206, 170, 229, 16, 44, 55, 2, 2, 82, 147, 46, 148, 135, 89, 120, 75, 192, 245, 179, 208, 101, 211, 163, 42, 66, 5, 240, 155, 5, 109, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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