Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 608a3a0a508377db631617f545dc0b9d7ea319ab84b4d706b74a3175b165bfa4

Tx prefix hash: 4eb675d22752c33080d6311d4a863dc9d6d97a2f1bc1c4f71cd31aa200793dc5
Tx public key: 939a09a8d57c065e0e9db3cc5ea0c35355b406bb8a519b7c5e2a0c01a4b75df7
Timestamp: 1748626595 Timestamp [UCT]: 2025-05-30 17:36:35 Age [y:d:h:m:s]: 00:164:07:38:18
Block: 1294347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115110 RingCT/type: yes/0
Extra: 01939a09a8d57c065e0e9db3cc5ea0c35355b406bb8a519b7c5e2a0c01a4b75df702110000000b43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47edcc6d74dfc1357ca754d0043ab734128f0d57c796160f02d6e337a95925db 0.600000000000 1781842 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": 1294357, "vin": [ { "gen": { "height": 1294347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47edcc6d74dfc1357ca754d0043ab734128f0d57c796160f02d6e337a95925db" } } ], "extra": [ 1, 147, 154, 9, 168, 213, 124, 6, 94, 14, 157, 179, 204, 94, 160, 195, 83, 85, 180, 6, 187, 138, 81, 155, 124, 94, 42, 12, 1, 164, 183, 93, 247, 2, 17, 0, 0, 0, 11, 67, 132, 109, 102, 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