Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f44c7e797ccdc327658bd5a7b7bb9ff74bcabf3c7f8a62b132c659d8b88929ec

Tx prefix hash: 66699b5750d9471e57236e01f71c1a486e973ac9eedd0faafec818e8d0a17e42
Tx public key: e187dbdca61812938b8b22d2c6580e455114ef2c85213cb91ea530afb0c7e9c6
Timestamp: 1658836536 Timestamp [UCT]: 2022-07-26 11:55:36 Age [y:d:h:m:s]: 03:098:08:04:08
Block: 552106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 850046 RingCT/type: yes/0
Extra: 01e187dbdca61812938b8b22d2c6580e455114ef2c85213cb91ea530afb0c7e9c6021100000013ec6d1a1a000000000000000000

1 output(s) for total of 9.091672037000 dcy

stealth address amount amount idx
00: 572f44f974b035e88c32b34ea3f0c563b7964a47efc733fcffa9ba579d8f8e4f 9.091672037000 983770 of 0

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": 552116, "vin": [ { "gen": { "height": 552106 } } ], "vout": [ { "amount": 9091672037, "target": { "key": "572f44f974b035e88c32b34ea3f0c563b7964a47efc733fcffa9ba579d8f8e4f" } } ], "extra": [ 1, 225, 135, 219, 220, 166, 24, 18, 147, 139, 139, 34, 210, 198, 88, 14, 69, 81, 20, 239, 44, 133, 33, 60, 185, 30, 165, 48, 175, 176, 199, 233, 198, 2, 17, 0, 0, 0, 19, 236, 109, 26, 26, 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