Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 361c471e0fe909d7921c0bb30108627fdfcff33e3ca5a27cf2cff594084f9e4a

Tx prefix hash: de74c0aea9d3310a56026b9fea0cc3d1b9caf22bf6953cc29e9de44db3961da1
Tx public key: 6ecd9ad7c74b7b6040031e98245c019453b73ddf27f3a42423de84ceb6deabc9
Timestamp: 1698122438 Timestamp [UCT]: 2023-10-24 04:40:38 Age [y:d:h:m:s]: 01:236:05:07:47
Block: 876387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429773 RingCT/type: yes/0
Extra: 016ecd9ad7c74b7b6040031e98245c019453b73ddf27f3a42423de84ceb6deabc9021100000011faf35c9c000000000000000000

1 output(s) for total of 0.765889440000 dcy

stealth address amount amount idx
00: 53b5f84bed0e28a75414a9c441e324d5776275c4b24c462145066ff8d0a744f0 0.765889440000 1331707 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": 876397, "vin": [ { "gen": { "height": 876387 } } ], "vout": [ { "amount": 765889440, "target": { "key": "53b5f84bed0e28a75414a9c441e324d5776275c4b24c462145066ff8d0a744f0" } } ], "extra": [ 1, 110, 205, 154, 215, 199, 75, 123, 96, 64, 3, 30, 152, 36, 92, 1, 148, 83, 183, 61, 223, 39, 243, 164, 36, 35, 222, 132, 206, 182, 222, 171, 201, 2, 17, 0, 0, 0, 17, 250, 243, 92, 156, 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