Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95b34c04a900a3c82ca1fd9285a1480558ed30a24da2a99866ee0152cd228ef5

Tx prefix hash: 0e99ce8ddbe21e2c3bef1e682f5e7e548ecb724c1f8e04088039dbab75c438eb
Tx public key: cf808714db9d73e04a620bc90bf51e3708afb62d7d154963c14df35ab386767c
Timestamp: 1701076506 Timestamp [UCT]: 2023-11-27 09:15:06 Age [y:d:h:m:s]: 01:201:20:38:45
Block: 900666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405385 RingCT/type: yes/0
Extra: 01cf808714db9d73e04a620bc90bf51e3708afb62d7d154963c14df35ab386767c021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.636384569000 dcy

stealth address amount amount idx
00: 95794031eb9be02115f795dcb5c8c2e0746f7d742ae09c3e64cdf92b820b5d68 0.636384569000 1357177 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": 900676, "vin": [ { "gen": { "height": 900666 } } ], "vout": [ { "amount": 636384569, "target": { "key": "95794031eb9be02115f795dcb5c8c2e0746f7d742ae09c3e64cdf92b820b5d68" } } ], "extra": [ 1, 207, 128, 135, 20, 219, 157, 115, 224, 74, 98, 11, 201, 11, 245, 30, 55, 8, 175, 182, 45, 125, 21, 73, 99, 193, 77, 243, 90, 179, 134, 118, 124, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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