Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecb906622ecaf304246555e703163de3774ceb6a7ebfc9aa671fa0918d3ccae1

Tx prefix hash: 3d4a22b758aaf1a2d82d6dc5882e84b25a810aa49c342fb4c86f56423e6969d4
Tx public key: 1e9788f6ddacf87ff248f3e438724bc4ac7244760dfc8884abd093f0e6b66aa3
Timestamp: 1750899168 Timestamp [UCT]: 2025-06-26 00:52:48 Age [y:d:h:m:s]: 00:141:07:57:42
Block: 1312849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98988 RingCT/type: yes/0
Extra: 011e9788f6ddacf87ff248f3e438724bc4ac7244760dfc8884abd093f0e6b66aa30211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5db1cf144dd50effc44f861fe9c4a1ae709fb932bc455a053ae7e3c60302a087 0.600000000000 1800484 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": 1312859, "vin": [ { "gen": { "height": 1312849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5db1cf144dd50effc44f861fe9c4a1ae709fb932bc455a053ae7e3c60302a087" } } ], "extra": [ 1, 30, 151, 136, 246, 221, 172, 248, 127, 242, 72, 243, 228, 56, 114, 75, 196, 172, 114, 68, 118, 13, 252, 136, 132, 171, 208, 147, 240, 230, 182, 106, 163, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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