Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a0dcaf93702cc1206031299f5b7f120e5386a47d90ba732c8e1f6b77598c676

Tx prefix hash: 70ef8e3323c57d7b2911885fe5bd02fa92574ef88679e6af994704c3f21c80c0
Tx public key: c988e282e3156bd751d9bf0b4ba25b072e1016908190e3d901dbcdf07432b473
Timestamp: 1701509269 Timestamp [UCT]: 2023-12-02 09:27:49 Age [y:d:h:m:s]: 01:196:02:37:56
Block: 904255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401262 RingCT/type: yes/0
Extra: 01c988e282e3156bd751d9bf0b4ba25b072e1016908190e3d901dbcdf07432b47302110000000375e3f0e9000000000000000000

1 output(s) for total of 0.619195495000 dcy

stealth address amount amount idx
00: 37d4065bbba77422a4b7b507f52eaffb63aee7cb2e7e84dce861c63480f1b3e0 0.619195495000 1360970 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": 904265, "vin": [ { "gen": { "height": 904255 } } ], "vout": [ { "amount": 619195495, "target": { "key": "37d4065bbba77422a4b7b507f52eaffb63aee7cb2e7e84dce861c63480f1b3e0" } } ], "extra": [ 1, 201, 136, 226, 130, 227, 21, 107, 215, 81, 217, 191, 11, 75, 162, 91, 7, 46, 16, 22, 144, 129, 144, 227, 217, 1, 219, 205, 240, 116, 50, 180, 115, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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