Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c419670261c1efddbdb5cdfd2bcea79663a05eeb70cb2cdf4e29cc3f01c1086c

Tx prefix hash: f96c214950b8f5c31a393e6f48605f823bd04f9c2b0e01c0ec080eeacabee525
Tx public key: 8730c37eca66c6c7aa2e0a704b34c0180748949f38d843ee04a54cc62e1313fc
Timestamp: 1748947272 Timestamp [UCT]: 2025-06-03 10:41:12 Age [y:d:h:m:s]: 00:176:04:09:59
Block: 1297002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123602 RingCT/type: yes/0
Extra: 018730c37eca66c6c7aa2e0a704b34c0180748949f38d843ee04a54cc62e1313fc02110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0da0dd67e529d143392a1adf7c99db790ba72fb6b33083c1962e6368e0d8d32 0.600000000000 1784519 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": 1297012, "vin": [ { "gen": { "height": 1297002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0da0dd67e529d143392a1adf7c99db790ba72fb6b33083c1962e6368e0d8d32" } } ], "extra": [ 1, 135, 48, 195, 126, 202, 102, 198, 199, 170, 46, 10, 112, 75, 52, 192, 24, 7, 72, 148, 159, 56, 216, 67, 238, 4, 165, 76, 198, 46, 19, 19, 252, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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