Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dfae1925c25157791aa6f98e5f68cf9e14fa99ad2f467dde58163ef24a88d6d

Tx prefix hash: 7d3b2379e090f23e047291ae35ea65322536cf854c8d6f5feb36b1348380bdc8
Tx public key: 37a7e9e81580ca7da4cfea690abfe672fab2ecef6e564250a92d4b7bfa2f75c4
Timestamp: 1712856569 Timestamp [UCT]: 2024-04-11 17:29:29 Age [y:d:h:m:s]: 01:203:05:40:17
Block: 998308 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403939 RingCT/type: yes/0
Extra: 0137a7e9e81580ca7da4cfea690abfe672fab2ecef6e564250a92d4b7bfa2f75c40211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17c5a83a8fab485184d6dc2ef42f4fbab730c2c4d685c705aa54dd81d9668119 0.600000000000 1458754 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": 998318, "vin": [ { "gen": { "height": 998308 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17c5a83a8fab485184d6dc2ef42f4fbab730c2c4d685c705aa54dd81d9668119" } } ], "extra": [ 1, 55, 167, 233, 232, 21, 128, 202, 125, 164, 207, 234, 105, 10, 191, 230, 114, 250, 178, 236, 239, 110, 86, 66, 80, 169, 45, 75, 123, 250, 47, 117, 196, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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