Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 401c68029bbc764018754c21a16e88e202fd4a2e2704a9d0b22200fa4ecda433

Tx prefix hash: 0c1f23c72a485eb3c09a184fa54e4a3e4e6a08ef267ee4c7ecfff22a5e112f59
Tx public key: e7b03c07f2a7d47a9e0ac8a0f9fca7e5da5ca66f28408ef386627d00550d1f90
Timestamp: 1751737393 Timestamp [UCT]: 2025-07-05 17:43:13 Age [y:d:h:m:s]: 00:129:15:32:00
Block: 1319405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91005 RingCT/type: yes/0
Extra: 01e7b03c07f2a7d47a9e0ac8a0f9fca7e5da5ca66f28408ef386627d00550d1f900211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e1b6c094051e1fdccfe656df702f5bae0fb8ae6917c80442e119daaaed06221 0.600000000000 1807096 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": 1319415, "vin": [ { "gen": { "height": 1319405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e1b6c094051e1fdccfe656df702f5bae0fb8ae6917c80442e119daaaed06221" } } ], "extra": [ 1, 231, 176, 60, 7, 242, 167, 212, 122, 158, 10, 200, 160, 249, 252, 167, 229, 218, 92, 166, 111, 40, 64, 142, 243, 134, 98, 125, 0, 85, 13, 31, 144, 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