Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6178f33017e7f43bd5850248af9eb56301bf9abc8f2e5ef39a1105b1ccbe474

Tx prefix hash: 68c5a78fa7f9f208a8a9114eee934926350522d2bd514821b6f1c15b1b3c5983
Tx public key: aca38e05b3e6e9798014e0d1d7de4f6751802721fad5582f27fb3208cca02c59
Timestamp: 1701567769 Timestamp [UCT]: 2023-12-03 01:42:49 Age [y:d:h:m:s]: 01:146:09:57:21
Block: 904741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365818 RingCT/type: yes/0
Extra: 01aca38e05b3e6e9798014e0d1d7de4f6751802721fad5582f27fb3208cca02c5902110000000633af99f4000000000000000000

1 output(s) for total of 0.616903831000 dcy

stealth address amount amount idx
00: 1aecd3b026320d26fa41915dc824f07b5890a1e12ccf22a83c302ca82a96f8ea 0.616903831000 1361514 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": 904751, "vin": [ { "gen": { "height": 904741 } } ], "vout": [ { "amount": 616903831, "target": { "key": "1aecd3b026320d26fa41915dc824f07b5890a1e12ccf22a83c302ca82a96f8ea" } } ], "extra": [ 1, 172, 163, 142, 5, 179, 230, 233, 121, 128, 20, 224, 209, 215, 222, 79, 103, 81, 128, 39, 33, 250, 213, 88, 47, 39, 251, 50, 8, 204, 160, 44, 89, 2, 17, 0, 0, 0, 6, 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