Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ab146db731e609d81852ca925ccfa70935a037547f6a0725b70e4fc0e75174f

Tx prefix hash: d0292239ad973887a2a15fc417205054372fd4d6cd9a42405c274fbd272d34bb
Tx public key: 55654b5b634010471a075f32a1418af7b8efb3997535278a6924c997ba3d18a0
Timestamp: 1694031180 Timestamp [UCT]: 2023-09-06 20:13:00 Age [y:d:h:m:s]: 01:071:08:45:25
Block: 842443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312307 RingCT/type: yes/0
Extra: 0155654b5b634010471a075f32a1418af7b8efb3997535278a6924c997ba3d18a0021100000008faf35c9c000000000000000000

1 output(s) for total of 0.992285612000 dcy

stealth address amount amount idx
00: f7abba08f1ddc5d451b3247e51e2a00cdb2c7e434b5062d602e7b0ada049b73d 0.992285612000 1295565 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": 842453, "vin": [ { "gen": { "height": 842443 } } ], "vout": [ { "amount": 992285612, "target": { "key": "f7abba08f1ddc5d451b3247e51e2a00cdb2c7e434b5062d602e7b0ada049b73d" } } ], "extra": [ 1, 85, 101, 75, 91, 99, 64, 16, 71, 26, 7, 95, 50, 161, 65, 138, 247, 184, 239, 179, 153, 117, 53, 39, 138, 105, 36, 201, 151, 186, 61, 24, 160, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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