Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d29e18e28595076cfd885eb627f7f7d6ed069522f72508c573070b23801a2ba4

Tx prefix hash: d1eacef3dc815a6592ddf90426dda496aa7d45f9a6d52f45c422a236d10a65cb
Tx public key: dcae1ace6a3ae94ce080285dcc3a8f279fe670d8da476e1a374333fc41b1f9a1
Timestamp: 1672961916 Timestamp [UCT]: 2023-01-05 23:38:36 Age [y:d:h:m:s]: 01:331:21:07:21
Block: 668452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498220 RingCT/type: yes/0
Extra: 01dcae1ace6a3ae94ce080285dcc3a8f279fe670d8da476e1a374333fc41b1f9a102110000000252542ceb000000000000000000

1 output(s) for total of 3.742320649000 dcy

stealth address amount amount idx
00: 7c39f87eb2f77d9cadf1c1f674a43edc41fbcaa5f84b99d668f68a66ab61dd73 3.742320649000 1109703 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": 668462, "vin": [ { "gen": { "height": 668452 } } ], "vout": [ { "amount": 3742320649, "target": { "key": "7c39f87eb2f77d9cadf1c1f674a43edc41fbcaa5f84b99d668f68a66ab61dd73" } } ], "extra": [ 1, 220, 174, 26, 206, 106, 58, 233, 76, 224, 128, 40, 93, 204, 58, 143, 39, 159, 230, 112, 216, 218, 71, 110, 26, 55, 67, 51, 252, 65, 177, 249, 161, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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