Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f9f68d16cb19f56b85801c4a09f319c0b4c97b5e854788afc6194edfd794557

Tx prefix hash: 2968a4786a2983f83f7ebebc0c99300561c2f0205127dc3f53405813ed53cdfb
Tx public key: 8caa903b62460df41b876e9c5ea9556e7d7844b3d1769e672a20359bc52169ac
Timestamp: 1697216184 Timestamp [UCT]: 2023-10-13 16:56:24 Age [y:d:h:m:s]: 02:055:12:31:00
Block: 868867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 559333 RingCT/type: yes/0
Extra: 018caa903b62460df41b876e9c5ea9556e7d7844b3d1769e672a20359bc52169ac02110000000433af99f4000000000000000000

1 output(s) for total of 0.811116011000 dcy

stealth address amount amount idx
00: 9cc3e09562b14a83ce8c7e0c0ef362486d3dbbaf0ed618b656d7811bab31e20b 0.811116011000 1323688 of 0

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": 868877, "vin": [ { "gen": { "height": 868867 } } ], "vout": [ { "amount": 811116011, "target": { "key": "9cc3e09562b14a83ce8c7e0c0ef362486d3dbbaf0ed618b656d7811bab31e20b" } } ], "extra": [ 1, 140, 170, 144, 59, 98, 70, 13, 244, 27, 135, 110, 156, 94, 169, 85, 110, 125, 120, 68, 179, 209, 118, 158, 103, 42, 32, 53, 155, 197, 33, 105, 172, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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