Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65045f9c68f0d64916deb662ffb42e72d5a160446c1b20536005765481d13e53

Tx prefix hash: db8c98e93a804fbcc2e8dd44ddcd5beea9aecc1da244b7aa686586e0b7498e49
Tx public key: 7beaca96c3c878e888a79e2fef88732b8abd6a28a16ff6ed1d6a7ef0d65a6374
Timestamp: 1736973664 Timestamp [UCT]: 2025-01-15 20:41:04 Age [y:d:h:m:s]: 00:057:02:41:59
Block: 1198121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40610 RingCT/type: yes/0
Extra: 017beaca96c3c878e888a79e2fef88732b8abd6a28a16ff6ed1d6a7ef0d65a63740211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ddc7c9d7fdbc950f2c2baa67f75c45958835ab816fbc65aa034c29a663419cb 0.600000000000 1684740 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": 1198131, "vin": [ { "gen": { "height": 1198121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ddc7c9d7fdbc950f2c2baa67f75c45958835ab816fbc65aa034c29a663419cb" } } ], "extra": [ 1, 123, 234, 202, 150, 195, 200, 120, 232, 136, 167, 158, 47, 239, 136, 115, 43, 138, 189, 106, 40, 161, 111, 246, 237, 29, 106, 126, 240, 214, 90, 99, 116, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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