Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a625cbf48351c78436591cffcf3ace1e0537923a310feb154f59a292b3517d45

Tx prefix hash: 969e7f48777b0355e2437578a67ec5f99fdcf666ecd3052bd54126cdc11dd30b
Tx public key: f70d0e9a2a3a2ed9091f9ae91a085ea3eef311f6812a33d14e41f14b84746008
Timestamp: 1750743115 Timestamp [UCT]: 2025-06-24 05:31:55 Age [y:d:h:m:s]: 00:149:16:54:49
Block: 1311603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104927 RingCT/type: yes/0
Extra: 01f70d0e9a2a3a2ed9091f9ae91a085ea3eef311f6812a33d14e41f14b84746008021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75b52634481af2173c2fd0ebe51e86aafda19575afbfcd6864b8c6c77d8bb130 0.600000000000 1799230 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": 1311613, "vin": [ { "gen": { "height": 1311603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75b52634481af2173c2fd0ebe51e86aafda19575afbfcd6864b8c6c77d8bb130" } } ], "extra": [ 1, 247, 13, 14, 154, 42, 58, 46, 217, 9, 31, 154, 233, 26, 8, 94, 163, 238, 243, 17, 246, 129, 42, 51, 209, 78, 65, 241, 75, 132, 116, 96, 8, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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