Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59dd00d56e1f45fa4b95d30abc9baf151058a960dab5089cefaf03e0693a566e

Tx prefix hash: df5f7bc0d86d3b52218e6f2bb6188024354b2255c1b46128427c464c8b302f03
Tx public key: 4918ae2dad35869c7b397e92a2575cbff0dd9ada2ad3be458346dfe3ff4d7763
Timestamp: 1694722024 Timestamp [UCT]: 2023-09-14 20:07:04 Age [y:d:h:m:s]: 01:198:11:06:26
Block: 848177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402926 RingCT/type: yes/0
Extra: 014918ae2dad35869c7b397e92a2575cbff0dd9ada2ad3be458346dfe3ff4d7763021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.949811806000 dcy

stealth address amount amount idx
00: e387a8d416f71d9e22764746075a1b2a108a1cafa63549d6afcadeb43ccea5da 0.949811806000 1301763 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": 848187, "vin": [ { "gen": { "height": 848177 } } ], "vout": [ { "amount": 949811806, "target": { "key": "e387a8d416f71d9e22764746075a1b2a108a1cafa63549d6afcadeb43ccea5da" } } ], "extra": [ 1, 73, 24, 174, 45, 173, 53, 134, 156, 123, 57, 126, 146, 162, 87, 92, 191, 240, 221, 154, 218, 42, 211, 190, 69, 131, 70, 223, 227, 255, 77, 119, 99, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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