Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca7f8fcaaab287976f94633b2620d21c3b0576f4a3c8a20f4e1832186af79a15

Tx prefix hash: 3fe9455c5c174d2b24e3c19d5091a07d585f2329122e05bd8b65ba14d2261420
Tx public key: 9fd38d9be373712385cc9c206a52ebdf1d653b9751b8e00c15d483e9ec272287
Timestamp: 1672057787 Timestamp [UCT]: 2022-12-26 12:29:47 Age [y:d:h:m:s]: 02:061:19:40:19
Block: 660979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 565821 RingCT/type: yes/0
Extra: 019fd38d9be373712385cc9c206a52ebdf1d653b9751b8e00c15d483e9ec27228702110000000133af99f4000000000000000000

1 output(s) for total of 3.961887670000 dcy

stealth address amount amount idx
00: 85786eb4b50bb29e06acd3a984a7de9a24a11e27b14b6c862bf1cf721c0e8d98 3.961887670000 1101726 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": 660989, "vin": [ { "gen": { "height": 660979 } } ], "vout": [ { "amount": 3961887670, "target": { "key": "85786eb4b50bb29e06acd3a984a7de9a24a11e27b14b6c862bf1cf721c0e8d98" } } ], "extra": [ 1, 159, 211, 141, 155, 227, 115, 113, 35, 133, 204, 156, 32, 106, 82, 235, 223, 29, 101, 59, 151, 81, 184, 224, 12, 21, 212, 131, 233, 236, 39, 34, 135, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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