Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91a2f609b59b4a559538453ac12e5aad89d44de9a929feeecc8e831cc53c0072

Tx prefix hash: b07d91c2333ef975888f23aa06263ca05c6181abbdc919192300230f1b1d4211
Tx public key: c5663c346df1ae6b1ad4a50240259e08c8bdb4ce6b01ba70dc85480427a980f9
Timestamp: 1681480884 Timestamp [UCT]: 2023-04-14 14:01:24 Age [y:d:h:m:s]: 01:215:22:50:37
Block: 738456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415798 RingCT/type: yes/0
Extra: 01c5663c346df1ae6b1ad4a50240259e08c8bdb4ce6b01ba70dc85480427a980f9021100000004b3164c24000000000000000000

1 output(s) for total of 2.193759146000 dcy

stealth address amount amount idx
00: a1a9019cc0d4cf7461d89fdebe023c6ec970109c32737cb54989158ac2ce4ecc 2.193759146000 1185143 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": 738466, "vin": [ { "gen": { "height": 738456 } } ], "vout": [ { "amount": 2193759146, "target": { "key": "a1a9019cc0d4cf7461d89fdebe023c6ec970109c32737cb54989158ac2ce4ecc" } } ], "extra": [ 1, 197, 102, 60, 52, 109, 241, 174, 107, 26, 212, 165, 2, 64, 37, 158, 8, 200, 189, 180, 206, 107, 1, 186, 112, 220, 133, 72, 4, 39, 169, 128, 249, 2, 17, 0, 0, 0, 4, 179, 22, 76, 36, 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