Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7de7d4ccd6c39540721f6495c36250eb2f5eb237967daa507579a69f4ba5190

Tx prefix hash: c3597fd831f4de7c162d9d3e57b9df13eeafe185b1a8b76607cb6a4c5c8e576d
Tx public key: b68f1fe597774d8578d7c804653c18ac6b530d0f2b66b2086d25eb2e4e4939a8
Timestamp: 1751109693 Timestamp [UCT]: 2025-06-28 11:21:33 Age [y:d:h:m:s]: 00:152:05:50:33
Block: 1314489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106917 RingCT/type: yes/0
Extra: 01b68f1fe597774d8578d7c804653c18ac6b530d0f2b66b2086d25eb2e4e4939a8021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d82006dc4d78a214ca008c0fc737dc403c179cdeff85e21a0e2197ea904d2f40 0.600000000000 1802136 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": 1314499, "vin": [ { "gen": { "height": 1314489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d82006dc4d78a214ca008c0fc737dc403c179cdeff85e21a0e2197ea904d2f40" } } ], "extra": [ 1, 182, 143, 31, 229, 151, 119, 77, 133, 120, 215, 200, 4, 101, 60, 24, 172, 107, 83, 13, 15, 43, 102, 178, 8, 109, 37, 235, 46, 78, 73, 57, 168, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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