Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c7e18c42e6eb6c119982d5db63ebdfbc2e64d04ac9fafaf364c0b946b3a181d

Tx prefix hash: fd3a8fd6ffd1ea5af6371bd92ff279299bfab0f9668e1c1767c8e389e8e5fa4a
Tx public key: 7585e511f5ccd7bff6141208720107bb7702f6ef6c6d08506743ae96af178be0
Timestamp: 1755910828 Timestamp [UCT]: 2025-08-23 01:00:28 Age [y:d:h:m:s]: 00:038:18:32:50
Block: 1352350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27570 RingCT/type: yes/0
Extra: 017585e511f5ccd7bff6141208720107bb7702f6ef6c6d08506743ae96af178be00211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34724c26c0dcd6ad3af8657e44607a8db2cc648b1ef0ed82fe6d710f109d645b 0.600000000000 1840313 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": 1352360, "vin": [ { "gen": { "height": 1352350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34724c26c0dcd6ad3af8657e44607a8db2cc648b1ef0ed82fe6d710f109d645b" } } ], "extra": [ 1, 117, 133, 229, 17, 245, 204, 215, 191, 246, 20, 18, 8, 114, 1, 7, 187, 119, 2, 246, 239, 108, 109, 8, 80, 103, 67, 174, 150, 175, 23, 139, 224, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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