Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d368d3788718e64b9aab968ef4051ee4afd1f92b445e95b660fc49e815f5f3c

Tx prefix hash: 92544e82be0955a46799837d8e9e0167c12f2aa50fc2af4597b665faabf15f38
Tx public key: 7c4cc233cac5d64d70db5a45fce48617052eaceb20fce6e3adc83558674f6c4f
Timestamp: 1733736350 Timestamp [UCT]: 2024-12-09 09:25:50 Age [y:d:h:m:s]: 00:100:02:12:27
Block: 1171338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71337 RingCT/type: yes/0
Extra: 017c4cc233cac5d64d70db5a45fce48617052eaceb20fce6e3adc83558674f6c4f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9ae10f0fd76b8f2e62d8ea6494c04e5a89d4e17dbb864c4a7506908ef2cd8cb 0.600000000000 1657079 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": 1171348, "vin": [ { "gen": { "height": 1171338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9ae10f0fd76b8f2e62d8ea6494c04e5a89d4e17dbb864c4a7506908ef2cd8cb" } } ], "extra": [ 1, 124, 76, 194, 51, 202, 197, 214, 77, 112, 219, 90, 69, 252, 228, 134, 23, 5, 46, 172, 235, 32, 252, 230, 227, 173, 200, 53, 88, 103, 79, 108, 79, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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