Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9cb13b489e40feeed5d7c1e24048aa2ce6b00847dee27c14c911dfb24e5b0e9

Tx prefix hash: 11b857a063c15174cb58c73cd5b7aac6a007db40fb02ce8070a1aeca45451e61
Tx public key: 8375848d6e2577a303c189f8b9a2b2a09ea8a6ebc03f3df4e0f9260d7e35b0a2
Timestamp: 1731202624 Timestamp [UCT]: 2024-11-10 01:37:04 Age [y:d:h:m:s]: 00:130:07:14:58
Block: 1150352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92961 RingCT/type: yes/0
Extra: 018375848d6e2577a303c189f8b9a2b2a09ea8a6ebc03f3df4e0f9260d7e35b0a2021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5350fac7100a1ddd2800922227f93688fe63f52a434c8884ff2f4a2497febf6a 0.600000000000 1635641 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": 1150362, "vin": [ { "gen": { "height": 1150352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5350fac7100a1ddd2800922227f93688fe63f52a434c8884ff2f4a2497febf6a" } } ], "extra": [ 1, 131, 117, 132, 141, 110, 37, 119, 163, 3, 193, 137, 248, 185, 162, 178, 160, 158, 168, 166, 235, 192, 63, 61, 244, 224, 249, 38, 13, 126, 53, 176, 162, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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