Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a979a82d02ac6424040a19266a7afb4a6bf2c6a020379cc26a9c778cf1352051

Tx prefix hash: 01c666a892851854a1f35685dc41db8c1fe83dc95079988dcf2d135314397be3
Tx public key: e077ac9b704019e52623cd059d8a6205099a3f79c5ec7c7196515724b6fc8d41
Timestamp: 1636986748 Timestamp [UCT]: 2021-11-15 14:32:28 Age [y:d:h:m:s]: 03:354:15:08:07
Block: 374868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1029713 RingCT/type: yes/0
Extra: 01e077ac9b704019e52623cd059d8a6205099a3f79c5ec7c7196515724b6fc8d4102110000000506faf294000000000000000000

1 output(s) for total of 35.148523655000 dcy

stealth address amount amount idx
00: fcac390b8da705f3af58402f35fb6fa7527a93df02dc6bbc06c881adacdb28a2 35.148523655000 758672 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": 374878, "vin": [ { "gen": { "height": 374868 } } ], "vout": [ { "amount": 35148523655, "target": { "key": "fcac390b8da705f3af58402f35fb6fa7527a93df02dc6bbc06c881adacdb28a2" } } ], "extra": [ 1, 224, 119, 172, 155, 112, 64, 25, 229, 38, 35, 205, 5, 157, 138, 98, 5, 9, 154, 63, 121, 197, 236, 124, 113, 150, 81, 87, 36, 182, 252, 141, 65, 2, 17, 0, 0, 0, 5, 6, 250, 242, 148, 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