Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed424e7cf2c5fe3e8d42cbedd5bbb444a199f1448dee4393b5cafa66e3451b58

Tx prefix hash: e473e9dba56a98588f0b0f90934c87293466fd7248d7969671e7183908e6948b
Tx public key: 385f4ae22988643d9577af3aa858135f32b44ce55e475d2cc48e2aa54afe8cd1
Timestamp: 1721493359 Timestamp [UCT]: 2024-07-20 16:35:59 Age [y:d:h:m:s]: 00:298:08:17:26
Block: 1069932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213179 RingCT/type: yes/0
Extra: 01385f4ae22988643d9577af3aa858135f32b44ce55e475d2cc48e2aa54afe8cd1021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 713d2704b9d70d3c8cbafd17d94ca9e129376ffd669e1e5c2d76d771471caaa7 0.600000000000 1541557 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": 1069942, "vin": [ { "gen": { "height": 1069932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "713d2704b9d70d3c8cbafd17d94ca9e129376ffd669e1e5c2d76d771471caaa7" } } ], "extra": [ 1, 56, 95, 74, 226, 41, 136, 100, 61, 149, 119, 175, 58, 168, 88, 19, 95, 50, 180, 76, 229, 94, 71, 93, 44, 196, 142, 42, 165, 74, 254, 140, 209, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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