Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ec1139bcd353bfd00edb09fa97356c7d7a347e69b0e14359a9dbb9823e91e7c

Tx prefix hash: be54e51ffe659a2a9bcd4cff726fffe526919569b10b9a3bd8e9dfadd13097d3
Tx public key: a4bee57f2f400debe00887b50651f16d7fab407e6023cbc7874666f34c5f914f
Timestamp: 1726886410 Timestamp [UCT]: 2024-09-21 02:40:10 Age [y:d:h:m:s]: 00:196:17:08:35
Block: 1114651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140406 RingCT/type: yes/0
Extra: 01a4bee57f2f400debe00887b50651f16d7fab407e6023cbc7874666f34c5f914f02110000000b144294a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1717f0c47aa2e8838ef962941507dd135be6eb7fd796a9fd7bea21f6bcdd6b2 0.600000000000 1594504 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": 1114661, "vin": [ { "gen": { "height": 1114651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1717f0c47aa2e8838ef962941507dd135be6eb7fd796a9fd7bea21f6bcdd6b2" } } ], "extra": [ 1, 164, 190, 229, 127, 47, 64, 13, 235, 224, 8, 135, 181, 6, 81, 241, 109, 127, 171, 64, 126, 96, 35, 203, 199, 135, 70, 102, 243, 76, 95, 145, 79, 2, 17, 0, 0, 0, 11, 20, 66, 148, 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