Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13ce09f6093d24e5a07e2b334d7609572f8b5edd00a02574d9e720aa2936b64c

Tx prefix hash: 59592f28ca60bdc9413d780942244eb3e0063cc18faf43902864b2206801f77c
Tx public key: d80f0a9f9d8c7cea198b73b5dc538d94e55b6b548c8180f6ce6e9efae99a0cec
Timestamp: 1727660429 Timestamp [UCT]: 2024-09-30 01:40:29 Age [y:d:h:m:s]: 00:211:16:48:31
Block: 1121064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151128 RingCT/type: yes/0
Extra: 01d80f0a9f9d8c7cea198b73b5dc538d94e55b6b548c8180f6ce6e9efae99a0cec02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c27bf3123fbf66d4d55fd289422a78077ad563eafdb66ee16c01a758088b174a 0.600000000000 1603203 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": 1121074, "vin": [ { "gen": { "height": 1121064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c27bf3123fbf66d4d55fd289422a78077ad563eafdb66ee16c01a758088b174a" } } ], "extra": [ 1, 216, 15, 10, 159, 157, 140, 124, 234, 25, 139, 115, 181, 220, 83, 141, 148, 229, 91, 107, 84, 140, 129, 128, 246, 206, 110, 158, 250, 233, 154, 12, 236, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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