Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f74f5973220ee1bde901a32ef745863cd5667e18cb95f811ef7a515f9fd2a2e5

Tx prefix hash: ca84cfc770b6cc68170b81f2c51d554d17b4f6b9031ea3e9a46df67b69421964
Tx public key: faefefac43fe68de0c2b59a0fb0107f4a97653c54606e0a00b44adb1c37ad2bd
Timestamp: 1699290957 Timestamp [UCT]: 2023-11-06 17:15:57 Age [y:d:h:m:s]: 01:199:22:12:05
Block: 885868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404122 RingCT/type: yes/0
Extra: 01faefefac43fe68de0c2b59a0fb0107f4a97653c54606e0a00b44adb1c37ad2bd02110000000233af99f4000000000000000000

1 output(s) for total of 0.712445387000 dcy

stealth address amount amount idx
00: 819aaadaef3bcc09022908ee0bfb472fb9604175cc6b7574090d309d738ed780 0.712445387000 1341661 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": 885878, "vin": [ { "gen": { "height": 885868 } } ], "vout": [ { "amount": 712445387, "target": { "key": "819aaadaef3bcc09022908ee0bfb472fb9604175cc6b7574090d309d738ed780" } } ], "extra": [ 1, 250, 239, 239, 172, 67, 254, 104, 222, 12, 43, 89, 160, 251, 1, 7, 244, 169, 118, 83, 197, 70, 6, 224, 160, 11, 68, 173, 177, 195, 122, 210, 189, 2, 17, 0, 0, 0, 2, 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