Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0afdce8b76eda97c83df978e10de49e15234ee8dc9105a204e85c5bfc532ac3c

Tx prefix hash: fc3521dbb67a3b1ee86cfc0af82a08101072130c507d16db218e24e7c2763bd0
Tx public key: 04dfbb61e28b401fba0c994f22fb6fa1b8aeefa61a82704d81dd1d46d5386980
Timestamp: 1741664518 Timestamp [UCT]: 2025-03-11 03:41:58 Age [y:d:h:m:s]: 00:322:08:53:15
Block: 1236707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228042 RingCT/type: yes/0
Extra: 0104dfbb61e28b401fba0c994f22fb6fa1b8aeefa61a82704d81dd1d46d5386980021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2121aa5dc97e2874a696a427f3cff0be3298b5c2491170d51db28f5375eff345 0.600000000000 1723658 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": 1236717, "vin": [ { "gen": { "height": 1236707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2121aa5dc97e2874a696a427f3cff0be3298b5c2491170d51db28f5375eff345" } } ], "extra": [ 1, 4, 223, 187, 97, 226, 139, 64, 31, 186, 12, 153, 79, 34, 251, 111, 161, 184, 174, 239, 166, 26, 130, 112, 77, 129, 221, 29, 70, 213, 56, 105, 128, 2, 17, 0, 0, 0, 7, 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