Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a7ef957675ccb9227130b5a142955e544c2dcb3341045c5ffb57a948308b317

Tx prefix hash: f388260856d8122f43711764371a2f3876d889ec45c7da71bf33d599853729ec
Tx public key: a82a41920c091e7418c88c4a81d1b8fc55f77baa2fc9e427b32fd907f23fe4c1
Timestamp: 1722653092 Timestamp [UCT]: 2024-08-03 02:44:52 Age [y:d:h:m:s]: 00:273:12:05:27
Block: 1079552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195382 RingCT/type: yes/0
Extra: 01a82a41920c091e7418c88c4a81d1b8fc55f77baa2fc9e427b32fd907f23fe4c1021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9f2babab663c9035f57b2d4e4f72b0eb9d7993ef3353ab7e4a54011d7481ab7 0.600000000000 1552555 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": 1079562, "vin": [ { "gen": { "height": 1079552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9f2babab663c9035f57b2d4e4f72b0eb9d7993ef3353ab7e4a54011d7481ab7" } } ], "extra": [ 1, 168, 42, 65, 146, 12, 9, 30, 116, 24, 200, 140, 74, 129, 209, 184, 252, 85, 247, 123, 170, 47, 201, 228, 39, 179, 47, 217, 7, 242, 63, 228, 193, 2, 17, 0, 0, 0, 2, 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