Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc977cc197c88b9d76e20792547324f04a9cbc91001ff290ade03c6406f5354c

Tx prefix hash: 91eb6fc87d6e295132a34c83125c482fb26b00f9263d8b8ed1f97ffd8fadc805
Tx public key: f629bac3b41bdad7874ca8f4c105884b9d3c2d54c04eb6cd10f720cb62e054d6
Timestamp: 1761973869 Timestamp [UCT]: 2025-11-01 05:11:09 Age [y:d:h:m:s]: 00:008:11:22:48
Block: 1402440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6052 RingCT/type: yes/0
Extra: 01f629bac3b41bdad7874ca8f4c105884b9d3c2d54c04eb6cd10f720cb62e054d6021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acc0c572cd758d82f337378b7c5fd9dd4c6b2a74e955f1aa0cc4f37b95c9cd78 0.600000000000 1890759 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": 1402450, "vin": [ { "gen": { "height": 1402440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acc0c572cd758d82f337378b7c5fd9dd4c6b2a74e955f1aa0cc4f37b95c9cd78" } } ], "extra": [ 1, 246, 41, 186, 195, 180, 27, 218, 215, 135, 76, 168, 244, 193, 5, 136, 75, 157, 60, 45, 84, 192, 78, 182, 205, 16, 247, 32, 203, 98, 224, 84, 214, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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