Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eade04a007e89d269419d4728839820b6d69c8a9b6b187d62f2c4d6119c056ab

Tx prefix hash: 06edc5e6442c221f75f07078aa3f8eebbcbd5c7466512a36105d77c853733316
Tx public key: 1a47e33b2d69a57b708b2cab6684384cf04ba87c96fec4ecce107fd745b310d2
Timestamp: 1582348588 Timestamp [UCT]: 2020-02-22 05:16:28 Age [y:d:h:m:s]: 04:311:09:08:00
Block: 70117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114942 RingCT/type: yes/0
Extra: 011a47e33b2d69a57b708b2cab6684384cf04ba87c96fec4ecce107fd745b310d20211000000024943cd9f000000000000000000

1 output(s) for total of 359.487495797000 dcy

stealth address amount amount idx
00: f9a826728cc7f43af5b9b09b3626f2b4f29b90a4f7c80c2af041deae48b44399 359.487495797000 129408 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": 70127, "vin": [ { "gen": { "height": 70117 } } ], "vout": [ { "amount": 359487495797, "target": { "key": "f9a826728cc7f43af5b9b09b3626f2b4f29b90a4f7c80c2af041deae48b44399" } } ], "extra": [ 1, 26, 71, 227, 59, 45, 105, 165, 123, 112, 139, 44, 171, 102, 132, 56, 76, 240, 75, 168, 124, 150, 254, 196, 236, 206, 16, 127, 215, 69, 179, 16, 210, 2, 17, 0, 0, 0, 2, 73, 67, 205, 159, 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