Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa3c72800379ad852edf3011ea59525377a6cdc1c4f532e41caecf4e717df4af

Tx prefix hash: 30f5b849717b14f4b721808d89cfa06ba461c3fefdd14e111fc3056afd20ee38
Tx public key: 66a80cfa30304eb44e7227584c8e32bcff8b2383e91edc44b46ab4fe7b59ec28
Timestamp: 1645484383 Timestamp [UCT]: 2022-02-21 22:59:43 Age [y:d:h:m:s]: 02:354:15:17:04
Block: 443650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 772619 RingCT/type: yes/0
Extra: 0166a80cfa30304eb44e7227584c8e32bcff8b2383e91edc44b46ab4fe7b59ec280211000000052e6b1fd5000000000000000000

1 output(s) for total of 20.797142626000 dcy

stealth address amount amount idx
00: b619f41bea5b8ef127f2a3aa23a77737bb17564df22f8c6c0ee401ec902ee700 20.797142626000 856739 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": 443660, "vin": [ { "gen": { "height": 443650 } } ], "vout": [ { "amount": 20797142626, "target": { "key": "b619f41bea5b8ef127f2a3aa23a77737bb17564df22f8c6c0ee401ec902ee700" } } ], "extra": [ 1, 102, 168, 12, 250, 48, 48, 78, 180, 78, 114, 39, 88, 76, 142, 50, 188, 255, 139, 35, 131, 233, 30, 220, 68, 180, 106, 180, 254, 123, 89, 236, 40, 2, 17, 0, 0, 0, 5, 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