Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37c0cf3f1870ad2d2854eec534c2eb61f9564c67adfe7fb687fd53cda1cee44c

Tx prefix hash: 1a2eb6c2fb5ce7f1f3059c56749f72e915a180bd179ba5db0405f97b7571fa6f
Tx public key: c5d0bfd16fac7eaf6294e51e634ff8d295e152a7ec8ae1b63d084723b19a5650
Timestamp: 1746453435 Timestamp [UCT]: 2025-05-05 13:57:15 Age [y:d:h:m:s]: 00:155:10:54:08
Block: 1276344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108749 RingCT/type: yes/0
Extra: 01c5d0bfd16fac7eaf6294e51e634ff8d295e152a7ec8ae1b63d084723b19a56500211000000051f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea3a8f07a2e480a80f669b368030a4f0683795cdf129df705b24293289748e3c 0.600000000000 1763679 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": 1276354, "vin": [ { "gen": { "height": 1276344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea3a8f07a2e480a80f669b368030a4f0683795cdf129df705b24293289748e3c" } } ], "extra": [ 1, 197, 208, 191, 209, 111, 172, 126, 175, 98, 148, 229, 30, 99, 79, 248, 210, 149, 225, 82, 167, 236, 138, 225, 182, 61, 8, 71, 35, 177, 154, 86, 80, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 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