Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 644737063a2870d0caa4c8224596624a79df20fe237302fbadd915b794b84c76

Tx prefix hash: a27c15b498eb297097177dc1c8d48f83cb1ea1fe583851191c1bb73609c7f03a
Tx public key: cbf0a1f7955b1f9efc74a0ab8a931fd24a21e88e50c866f8b1fa1bf5babbbb1d
Timestamp: 1745461321 Timestamp [UCT]: 2025-04-24 02:22:01 Age [y:d:h:m:s]: 00:217:21:09:23
Block: 1268125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153465 RingCT/type: yes/0
Extra: 01cbf0a1f7955b1f9efc74a0ab8a931fd24a21e88e50c866f8b1fa1bf5babbbb1d0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bb6e8e38316a322208c240bbeaea50f3e6cc1d6d9faf3ae177e57b3b287e768 0.600000000000 1755354 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": 1268135, "vin": [ { "gen": { "height": 1268125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bb6e8e38316a322208c240bbeaea50f3e6cc1d6d9faf3ae177e57b3b287e768" } } ], "extra": [ 1, 203, 240, 161, 247, 149, 91, 31, 158, 252, 116, 160, 171, 138, 147, 31, 210, 74, 33, 232, 142, 80, 200, 102, 248, 177, 250, 27, 245, 186, 187, 187, 29, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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