Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2339e0fc12d82a96ade70f849de69e90eacecdac4b8ce43d6844f4b59de6a723

Tx prefix hash: 267d2fcc6980fe61ff8eab17dbc075e8f4d877c4e2e02c74cc57013b0929e532
Tx public key: 4c1ce7f57a9111fa54b641b972f1e1e59ee4dafae5de2dff5774e483371aa4d5
Timestamp: 1763447656 Timestamp [UCT]: 2025-11-18 06:34:16 Age [y:d:h:m:s]: 00:009:23:16:59
Block: 1414627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7141 RingCT/type: yes/0
Extra: 014c1ce7f57a9111fa54b641b972f1e1e59ee4dafae5de2dff5774e483371aa4d502110000000143b50471000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9ef1dc7e151f845e413fe45243a000b3d6d67a6a2789eb480e9105cc8f7e8e8 0.600000000000 1903118 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": 1414637, "vin": [ { "gen": { "height": 1414627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9ef1dc7e151f845e413fe45243a000b3d6d67a6a2789eb480e9105cc8f7e8e8" } } ], "extra": [ 1, 76, 28, 231, 245, 122, 145, 17, 250, 84, 182, 65, 185, 114, 241, 225, 229, 158, 228, 218, 250, 229, 222, 45, 255, 87, 116, 228, 131, 55, 26, 164, 213, 2, 17, 0, 0, 0, 1, 67, 181, 4, 113, 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