Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3beb7b9649e62136ce04fc29cf7ad38ac482c88c9ba47553897a2de2d2e08ee

Tx prefix hash: 868d0d1fc9f97133279c45d1ef6db52f9e37c6d7e359aaf1952b2165e94401e6
Tx public key: 5d153a31f1d2f0d9f8cecdaf44f0826e55933775c0723341ebc4f0d9698dcbb2
Timestamp: 1716262998 Timestamp [UCT]: 2024-05-21 03:43:18 Age [y:d:h:m:s]: 01:169:10:14:54
Block: 1026583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379656 RingCT/type: yes/0
Extra: 015d153a31f1d2f0d9f8cecdaf44f0826e55933775c0723341ebc4f0d9698dcbb202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c774f2fe6f25ca9a8d1a923e456c5560734201fed8c2340e5423f20a65c79b5 0.600000000000 1493746 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": 1026593, "vin": [ { "gen": { "height": 1026583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c774f2fe6f25ca9a8d1a923e456c5560734201fed8c2340e5423f20a65c79b5" } } ], "extra": [ 1, 93, 21, 58, 49, 241, 210, 240, 217, 248, 206, 205, 175, 68, 240, 130, 110, 85, 147, 55, 117, 192, 114, 51, 65, 235, 196, 240, 217, 105, 141, 203, 178, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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