Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e3b4137d6b0e177eefe4b22e0da3c03c9324a2452a403a8a8bced2996546182

Tx prefix hash: c3e170c579f477687673f072edcd148cb169c412421f95f8e8c1ab3c7e9e1894
Tx public key: c07aeb74cf068ab6eb4f7c811fea0773797c9a8ac0befdfe431ee5a5fb128c5d
Timestamp: 1734147079 Timestamp [UCT]: 2024-12-14 03:31:19 Age [y:d:h:m:s]: 00:100:23:36:19
Block: 1174746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71940 RingCT/type: yes/0
Extra: 01c07aeb74cf068ab6eb4f7c811fea0773797c9a8ac0befdfe431ee5a5fb128c5d0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92e1452678bed26fe23b4eb405959d96c0ce27db66a1ce56b44afbb98227405c 0.600000000000 1660937 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": 1174756, "vin": [ { "gen": { "height": 1174746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92e1452678bed26fe23b4eb405959d96c0ce27db66a1ce56b44afbb98227405c" } } ], "extra": [ 1, 192, 122, 235, 116, 207, 6, 138, 182, 235, 79, 124, 129, 31, 234, 7, 115, 121, 124, 154, 138, 192, 190, 253, 254, 67, 30, 229, 165, 251, 18, 140, 93, 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