Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9493ab7ffbcfc109c5773339124dd54067db4166110d1932c16490f75a0a29af

Tx prefix hash: 0a6ffdc36c48cb55a3e3a8ecc5e0c1ba97ae4e18e2b9138e3be08c6027dac8da
Tx public key: 95be5cd594d2d2723cd35b1a43ce9d4bb7ffd8044caecfd3e875fa7329363425
Timestamp: 1729706437 Timestamp [UCT]: 2024-10-23 18:00:37 Age [y:d:h:m:s]: 00:141:21:16:35
Block: 1137996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101209 RingCT/type: yes/0
Extra: 0195be5cd594d2d2723cd35b1a43ce9d4bb7ffd8044caecfd3e875fa73293634250211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b43fa1aa49fe890ef23e2b3193ada779b9f0d8e657a302f9b7ddb74e0dd778b7 0.600000000000 1621593 of 15

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": 1138006, "vin": [ { "gen": { "height": 1137996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b43fa1aa49fe890ef23e2b3193ada779b9f0d8e657a302f9b7ddb74e0dd778b7" } } ], "extra": [ 1, 149, 190, 92, 213, 148, 210, 210, 114, 60, 211, 91, 26, 67, 206, 157, 75, 183, 255, 216, 4, 76, 174, 207, 211, 232, 117, 250, 115, 41, 54, 52, 37, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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