Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5583b0dc932216f5cf73f0eae9b1deebaf678f1dc83682485c998489cccd9ed8

Tx prefix hash: a08055431e3166b0405ab2fcb30f027f48e59f9a159ae11dd93caefbd43f775d
Tx public key: 703f3c823471143c2ebee5a79fdfdf84da1dfd4837a601c0b465d728fe75a59c
Timestamp: 1648330217 Timestamp [UCT]: 2022-03-26 21:30:17 Age [y:d:h:m:s]: 02:250:14:19:41
Block: 467039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 698642 RingCT/type: yes/0
Extra: 01703f3c823471143c2ebee5a79fdfdf84da1dfd4837a601c0b465d728fe75a59c0211000000102e6b1fd5000000000000000000

1 output(s) for total of 17.398274143000 dcy

stealth address amount amount idx
00: 1c76a4421a59c97f8ab5f464aee2ff63d5f4a88aea287f1c9b31c76ccc9d5317 17.398274143000 885466 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": 467049, "vin": [ { "gen": { "height": 467039 } } ], "vout": [ { "amount": 17398274143, "target": { "key": "1c76a4421a59c97f8ab5f464aee2ff63d5f4a88aea287f1c9b31c76ccc9d5317" } } ], "extra": [ 1, 112, 63, 60, 130, 52, 113, 20, 60, 46, 190, 229, 167, 159, 223, 223, 132, 218, 29, 253, 72, 55, 166, 1, 192, 180, 101, 215, 40, 254, 117, 165, 156, 2, 17, 0, 0, 0, 16, 46, 107, 31, 213, 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