Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 546b47a455f2d0a50c06260aef7b8dbac84e3105e941d6ebe3fc36f422f9a8cf

Tx prefix hash: e46d1f47a70625de707621a9b9c378576e357afd03ae60545384ca2d285e61ba
Tx public key: 1753487aca806e0183dfa43cb6ddf829cb04dfa6a013fa4730865a5c56015fb0
Timestamp: 1696747285 Timestamp [UCT]: 2023-10-08 06:41:25 Age [y:d:h:m:s]: 01:090:21:07:04
Block: 864986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326212 RingCT/type: yes/0
Extra: 011753487aca806e0183dfa43cb6ddf829cb04dfa6a013fa4730865a5c56015fb002110000000133af99f4000000000000000000

1 output(s) for total of 0.835492093000 dcy

stealth address amount amount idx
00: 94873ea5e8fbce5504e173eac40e8fcfb11cdbb8277d2f4dd8f04bc3675d84db 0.835492093000 1319512 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": 864996, "vin": [ { "gen": { "height": 864986 } } ], "vout": [ { "amount": 835492093, "target": { "key": "94873ea5e8fbce5504e173eac40e8fcfb11cdbb8277d2f4dd8f04bc3675d84db" } } ], "extra": [ 1, 23, 83, 72, 122, 202, 128, 110, 1, 131, 223, 164, 60, 182, 221, 248, 41, 203, 4, 223, 166, 160, 19, 250, 71, 48, 134, 90, 92, 86, 1, 95, 176, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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