Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85963cf561c69e2d996f95573c3b9c173366328c1f06ab09a9759b353e05fad0

Tx prefix hash: bb4072f04c6e7a50293bd429c79d9a612fa2aa38cf939a3c35cab67791f79801
Tx public key: af0d23740cff74b753d508f5c8b75056ec94e70af8eec373e1249360e7b113ba
Timestamp: 1676937398 Timestamp [UCT]: 2023-02-20 23:56:38 Age [y:d:h:m:s]: 01:273:11:42:19
Block: 701427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456367 RingCT/type: yes/0
Extra: 01af0d23740cff74b753d508f5c8b75056ec94e70af8eec373e1249360e7b113ba02110000000174b6d784000000000000000000

1 output(s) for total of 2.909920231000 dcy

stealth address amount amount idx
00: da4e585bb0c6aace24baa749f361a9f4ee2930bcd167b461e7b9c70adfc98780 2.909920231000 1144908 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": 701437, "vin": [ { "gen": { "height": 701427 } } ], "vout": [ { "amount": 2909920231, "target": { "key": "da4e585bb0c6aace24baa749f361a9f4ee2930bcd167b461e7b9c70adfc98780" } } ], "extra": [ 1, 175, 13, 35, 116, 12, 255, 116, 183, 83, 213, 8, 245, 200, 183, 80, 86, 236, 148, 231, 10, 248, 238, 195, 115, 225, 36, 147, 96, 231, 177, 19, 186, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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