Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0d345a433ac490b1b460280f510182a287f794a5204e9f51720032fe7a9aac2

Tx prefix hash: 8a25f476f5fc15d43211b2e5ad79a710159df9b7e3d7c8e7b9370e9ee78e63af
Tx public key: 83cb9c20cf12c54444a76f0f16a8658b543e853bf972a1806ba7651e01b24967
Timestamp: 1643544790 Timestamp [UCT]: 2022-01-30 12:13:10 Age [y:d:h:m:s]: 02:328:00:36:07
Block: 428468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 753007 RingCT/type: yes/0
Extra: 0183cb9c20cf12c54444a76f0f16a8658b543e853bf972a1806ba7651e01b249670211000000012e6b1fd5000000000000000000

1 output(s) for total of 23.351133180000 dcy

stealth address amount amount idx
00: 9882499a135d04783e5d7e05f78e690948605e35b7590dbb74ed174ded877b18 23.351133180000 837868 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": 428478, "vin": [ { "gen": { "height": 428468 } } ], "vout": [ { "amount": 23351133180, "target": { "key": "9882499a135d04783e5d7e05f78e690948605e35b7590dbb74ed174ded877b18" } } ], "extra": [ 1, 131, 203, 156, 32, 207, 18, 197, 68, 68, 167, 111, 15, 22, 168, 101, 139, 84, 62, 133, 59, 249, 114, 161, 128, 107, 167, 101, 30, 1, 178, 73, 103, 2, 17, 0, 0, 0, 1, 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