Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1933e485dbafdcbc90ce203f8b60a1cc4f5eb29b5c8dca30b0913b360c430d0c

Tx prefix hash: d4acfe17b6c6c40a67f503221f9c96a5cab22c9661953bf8a5582fa1fd7c6449
Tx public key: 79c341dfd08bf406acb594d61d4c1d446188cca8d02dd9c00203716e5de5dd2b
Timestamp: 1648493298 Timestamp [UCT]: 2022-03-28 18:48:18 Age [y:d:h:m:s]: 02:288:03:31:58
Block: 468384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 725505 RingCT/type: yes/0
Extra: 0179c341dfd08bf406acb594d61d4c1d446188cca8d02dd9c00203716e5de5dd2b021100000014d3fcec30000000000000000000

1 output(s) for total of 17.220653345000 dcy

stealth address amount amount idx
00: 1da2366cf3ea395a040a0bda336088b16028ea96c05967ce26cc548a4c29ae07 17.220653345000 887090 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": 468394, "vin": [ { "gen": { "height": 468384 } } ], "vout": [ { "amount": 17220653345, "target": { "key": "1da2366cf3ea395a040a0bda336088b16028ea96c05967ce26cc548a4c29ae07" } } ], "extra": [ 1, 121, 195, 65, 223, 208, 139, 244, 6, 172, 181, 148, 214, 29, 76, 29, 68, 97, 136, 204, 168, 208, 45, 217, 192, 2, 3, 113, 110, 93, 229, 221, 43, 2, 17, 0, 0, 0, 20, 211, 252, 236, 48, 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