Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a29bc3a0dc26d0f36d82c9712ba09fa2e6f0e361c57747ef10d507bc6393653

Tx prefix hash: 91beecb05a6cab15280953500f11b8d9eb7b857379e8d556832a3e0037e70b18
Tx public key: 58ddb4cbfb5615f8a70695d9579b84313d71ceb2e6346d8fb2225febdc2ef4d9
Timestamp: 1724657487 Timestamp [UCT]: 2024-08-26 07:31:27 Age [y:d:h:m:s]: 00:256:07:52:53
Block: 1096160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183081 RingCT/type: yes/0
Extra: 0158ddb4cbfb5615f8a70695d9579b84313d71ceb2e6346d8fb2225febdc2ef4d902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5846b7b91ca9a7c2295d8b7a8b2de6e322003cce81e80299940acbbd9ade7b2d 0.600000000000 1571347 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": 1096170, "vin": [ { "gen": { "height": 1096160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5846b7b91ca9a7c2295d8b7a8b2de6e322003cce81e80299940acbbd9ade7b2d" } } ], "extra": [ 1, 88, 221, 180, 203, 251, 86, 21, 248, 167, 6, 149, 217, 87, 155, 132, 49, 61, 113, 206, 178, 230, 52, 109, 143, 178, 34, 95, 235, 220, 46, 244, 217, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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