Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f0f0d9255fdf3185d22293626733cf2f266478c288654e4396151613ff46b32

Tx prefix hash: 6f336a760b619558c51c6ac27e367b5f1a95ba0351476a3d24002cf74b8e3f55
Tx public key: 8a85574e779d28d318d7307cbdd09772d5e7f37f2df1fa13b2e79e410864cb46
Timestamp: 1733261364 Timestamp [UCT]: 2024-12-03 21:29:24 Age [y:d:h:m:s]: 00:106:01:57:46
Block: 1167391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75646 RingCT/type: yes/0
Extra: 018a85574e779d28d318d7307cbdd09772d5e7f37f2df1fa13b2e79e410864cb460211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dad432d3f37ce2a97c81a99cb57692842b159d195a388acb8a79878174e2135 0.600000000000 1653086 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": 1167401, "vin": [ { "gen": { "height": 1167391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dad432d3f37ce2a97c81a99cb57692842b159d195a388acb8a79878174e2135" } } ], "extra": [ 1, 138, 133, 87, 78, 119, 157, 40, 211, 24, 215, 48, 124, 189, 208, 151, 114, 213, 231, 243, 127, 45, 241, 250, 19, 178, 231, 158, 65, 8, 100, 203, 70, 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