Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff75660681823de3aab7b0ec38589a6f91207930bf767f8637e09875cce7e3bb

Tx prefix hash: 9aa7c946443c08d702045789a27c4e44d679429f5a372a3323d32e1b1f176521
Tx public key: 44f7712ed8c57fb05d882d33e876ae4f58504284e575e548752b2eb2f9a46ff5
Timestamp: 1717216836 Timestamp [UCT]: 2024-06-01 04:40:36 Age [y:d:h:m:s]: 00:267:18:32:54
Block: 1034487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191332 RingCT/type: yes/0
Extra: 0144f7712ed8c57fb05d882d33e876ae4f58504284e575e548752b2eb2f9a46ff502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24d242c10ce41d3a30436c88a18a2309ed393ab3d9ead7513cf191ce8dfb091f 0.600000000000 1503000 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": 1034497, "vin": [ { "gen": { "height": 1034487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24d242c10ce41d3a30436c88a18a2309ed393ab3d9ead7513cf191ce8dfb091f" } } ], "extra": [ 1, 68, 247, 113, 46, 216, 197, 127, 176, 93, 136, 45, 51, 232, 118, 174, 79, 88, 80, 66, 132, 229, 117, 229, 72, 117, 43, 46, 178, 249, 164, 111, 245, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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