Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29617ff2051f5931185c77462729c56ca9d4c243cb1d2291d0fcef25027c7a42

Tx prefix hash: 69827194bd527e9536d36910d09a24e625ea662fa7df9675a6d3bf870c3e86c4
Tx public key: 5bf0d41ee00dfbf5bde08d0f0d7a0341633a15ffe8e709f9a7d7fadfe71e0c2a
Timestamp: 1747922045 Timestamp [UCT]: 2025-05-22 13:54:05 Age [y:d:h:m:s]: 00:181:18:24:58
Block: 1288514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127599 RingCT/type: yes/0
Extra: 015bf0d41ee00dfbf5bde08d0f0d7a0341633a15ffe8e709f9a7d7fadfe71e0c2a0211000000081f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fe49b98e0d9a7d63ba9a05d7fda1000510fb843e46e6f33b2225ecd8bc82904 0.600000000000 1775981 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": 1288524, "vin": [ { "gen": { "height": 1288514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fe49b98e0d9a7d63ba9a05d7fda1000510fb843e46e6f33b2225ecd8bc82904" } } ], "extra": [ 1, 91, 240, 212, 30, 224, 13, 251, 245, 189, 224, 141, 15, 13, 122, 3, 65, 99, 58, 21, 255, 232, 231, 9, 249, 167, 215, 250, 223, 231, 30, 12, 42, 2, 17, 0, 0, 0, 8, 31, 144, 81, 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