Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b03d35c6e929df8e573732f12ea84680a9db842a0e54afc6fceb49235e8add98

Tx prefix hash: e8582bd5085817bbb0feb5417f92fc965964605292176ed722abcee31fe2a3bf
Tx public key: 06e80f183a0ae84a9f9c1b3363ba03ff7068281c2769c5a7b4a45bafe13d7f39
Timestamp: 1726860317 Timestamp [UCT]: 2024-09-20 19:25:17 Age [y:d:h:m:s]: 00:193:00:50:00
Block: 1114431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137766 RingCT/type: yes/0
Extra: 0106e80f183a0ae84a9f9c1b3363ba03ff7068281c2769c5a7b4a45bafe13d7f390211000000032c3a34dc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70e67733f8414c1fdc1b9d20946c4e5fb75d3eb87ad2da1a395f5742cea94037 0.600000000000 1594232 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": 1114441, "vin": [ { "gen": { "height": 1114431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70e67733f8414c1fdc1b9d20946c4e5fb75d3eb87ad2da1a395f5742cea94037" } } ], "extra": [ 1, 6, 232, 15, 24, 58, 10, 232, 74, 159, 156, 27, 51, 99, 186, 3, 255, 112, 104, 40, 28, 39, 105, 197, 167, 180, 164, 91, 175, 225, 61, 127, 57, 2, 17, 0, 0, 0, 3, 44, 58, 52, 220, 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