Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6f142e3a2605ff1c017b49b07e73fe3408ed57a8e9e959bb59a2fe56409419a

Tx prefix hash: 3850a6c15a3d96d4eaf8793ad4c2cf17506e7a16e8c2611cd4f4ada97b8f50fd
Tx public key: e7b65ca2d9cba956ee5992dfb758ea905203ef1c69fab14c18fb204029b946e5
Timestamp: 1702135532 Timestamp [UCT]: 2023-12-09 15:25:32 Age [y:d:h:m:s]: 01:098:20:44:45
Block: 909451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331813 RingCT/type: yes/0
Extra: 01e7b65ca2d9cba956ee5992dfb758ea905203ef1c69fab14c18fb204029b946e502110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3398cb995f804aac86967b21fda937578fa5d57fa8ae53601a3d65e16ec79dc 0.600000000000 1366538 of 15

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": 909461, "vin": [ { "gen": { "height": 909451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3398cb995f804aac86967b21fda937578fa5d57fa8ae53601a3d65e16ec79dc" } } ], "extra": [ 1, 231, 182, 92, 162, 217, 203, 169, 86, 238, 89, 146, 223, 183, 88, 234, 144, 82, 3, 239, 28, 105, 250, 177, 76, 24, 251, 32, 64, 41, 185, 70, 229, 2, 17, 0, 0, 0, 7, 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