Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f144dc85c25cde6645ca387b37cc805f2cb0be3b88b31d9238ed3c9018461a87

Tx prefix hash: 5a8c6b8a7e9bb95e4595112b63b4c27f2ed2471e4115e445300b73e3ad211d48
Tx public key: 303ec448811ebbde1628a2a74782e5e830b1414e22d076fb9fb6c83e69e537b4
Timestamp: 1750557282 Timestamp [UCT]: 2025-06-22 01:54:42 Age [y:d:h:m:s]: 00:140:20:10:33
Block: 1310137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98520 RingCT/type: yes/0
Extra: 01303ec448811ebbde1628a2a74782e5e830b1414e22d076fb9fb6c83e69e537b4021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb0f88d24a3492e48930cc9a4bf6dcfd80b18b059a12746a473106866f976224 0.600000000000 1797756 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": 1310147, "vin": [ { "gen": { "height": 1310137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb0f88d24a3492e48930cc9a4bf6dcfd80b18b059a12746a473106866f976224" } } ], "extra": [ 1, 48, 62, 196, 72, 129, 30, 187, 222, 22, 40, 162, 167, 71, 130, 229, 232, 48, 177, 65, 78, 34, 208, 118, 251, 159, 182, 200, 62, 105, 229, 55, 180, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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