Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b01d68638301c20fc3f43d546689d5f3089d831f3fceb98ed6fa7c4c9a969d4

Tx prefix hash: 6fb3247b887714ee78d231ad0e057949ed3cfb605b0a2a08897806b29b893c82
Tx public key: 469ef7f01bef23fd4485c6f8735ff52b6d2efb35960d93513443aca416c9946c
Timestamp: 1735329024 Timestamp [UCT]: 2024-12-27 19:50:24 Age [y:d:h:m:s]: 00:085:01:35:12
Block: 1184511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60595 RingCT/type: yes/0
Extra: 01469ef7f01bef23fd4485c6f8735ff52b6d2efb35960d93513443aca416c9946c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac13f4a1940abfc35f4e5b4ec5702d77ebe129f2c48e2d17e234c91fae1f84e0 0.600000000000 1670968 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": 1184521, "vin": [ { "gen": { "height": 1184511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac13f4a1940abfc35f4e5b4ec5702d77ebe129f2c48e2d17e234c91fae1f84e0" } } ], "extra": [ 1, 70, 158, 247, 240, 27, 239, 35, 253, 68, 133, 198, 248, 115, 95, 245, 43, 109, 46, 251, 53, 150, 13, 147, 81, 52, 67, 172, 164, 22, 201, 148, 108, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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