Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52758755e4355bf74820a1dae275541777541a4f8442ca666d68c4c6353772a0

Tx prefix hash: 128ae23fead18195d1fdea7d0a0f33f9b34356ec92e77eb6babfcbf4505874bd
Tx public key: b2a4a5fcabf532031c6ac2d564138575bff98d012c74dee9c4a51610929ef4db
Timestamp: 1726358103 Timestamp [UCT]: 2024-09-14 23:55:03 Age [y:d:h:m:s]: 01:053:23:06:32
Block: 1110263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296987 RingCT/type: yes/0
Extra: 01b2a4a5fcabf532031c6ac2d564138575bff98d012c74dee9c4a51610929ef4db02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a79dbd78d31bef4c8d5f44c24de4aa71b34343d1e47a01351073b07e4d0d073 0.600000000000 1588808 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": 1110273, "vin": [ { "gen": { "height": 1110263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a79dbd78d31bef4c8d5f44c24de4aa71b34343d1e47a01351073b07e4d0d073" } } ], "extra": [ 1, 178, 164, 165, 252, 171, 245, 50, 3, 28, 106, 194, 213, 100, 19, 133, 117, 191, 249, 141, 1, 44, 116, 222, 233, 196, 165, 22, 16, 146, 158, 244, 219, 2, 17, 0, 0, 0, 4, 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