Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69beae8531710ea9e2d9c6da294705368e9deec055a30d678f9c7141fa25dc5a

Tx prefix hash: 52d518020fbd75efacd723064851556d6b04dfddd6d46415749b99911242b099
Tx public key: a53bc18f8a094e3442d6c5d483656b7d91939bba6cfc00eb2fffd4af75a53d62
Timestamp: 1634934416 Timestamp [UCT]: 2021-10-22 20:26:56 Age [y:d:h:m:s]: 03:141:17:44:22
Block: 358333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 879408 RingCT/type: yes/0
Extra: 01a53bc18f8a094e3442d6c5d483656b7d91939bba6cfc00eb2fffd4af75a53d62021100000003602d2cbd000000000000000000

1 output(s) for total of 39.874424799000 dcy

stealth address amount amount idx
00: ca1a5a482717d6297fc867eb62d4142f2eacd8b30bb1c87263b53336d9be3809 39.874424799000 730194 of 0

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": 358343, "vin": [ { "gen": { "height": 358333 } } ], "vout": [ { "amount": 39874424799, "target": { "key": "ca1a5a482717d6297fc867eb62d4142f2eacd8b30bb1c87263b53336d9be3809" } } ], "extra": [ 1, 165, 59, 193, 143, 138, 9, 78, 52, 66, 214, 197, 212, 131, 101, 107, 125, 145, 147, 155, 186, 108, 252, 0, 235, 47, 255, 212, 175, 117, 165, 61, 98, 2, 17, 0, 0, 0, 3, 96, 45, 44, 189, 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