Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc22143264af4142d1423ee7495c0153fba2e16431db41e32da61d96bfdac973

Tx prefix hash: 468d5e55d6f1b01a95942c8e1e1b82cc9c6fc9caf642cbd92d51414bf6c2ea92
Tx public key: ff429ef797d3cdc15536f8727785c801b1f32cb07f1a9b9e40e70f2c7f2d4dcf
Timestamp: 1726138902 Timestamp [UCT]: 2024-09-12 11:01:42 Age [y:d:h:m:s]: 00:218:06:58:14
Block: 1108444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155862 RingCT/type: yes/0
Extra: 01ff429ef797d3cdc15536f8727785c801b1f32cb07f1a9b9e40e70f2c7f2d4dcf02110000000291e13c04000000000000000000

1 output(s) for total of 0.607820000000 dcy

stealth address amount amount idx
00: a45f51d78c00a44a34382494941ce0f635a47c2ddb9113016fe782dc04ff4636 0.607820000000 1586343 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": 1108454, "vin": [ { "gen": { "height": 1108444 } } ], "vout": [ { "amount": 607820000, "target": { "key": "a45f51d78c00a44a34382494941ce0f635a47c2ddb9113016fe782dc04ff4636" } } ], "extra": [ 1, 255, 66, 158, 247, 151, 211, 205, 193, 85, 54, 248, 114, 119, 133, 200, 1, 177, 243, 44, 176, 127, 26, 155, 158, 64, 231, 15, 44, 127, 45, 77, 207, 2, 17, 0, 0, 0, 2, 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