Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf7b9d3e8d3cdcdb582d7fa81b0cf44b19cbcb9ee4b088ded4413069fcdd1cc4

Tx prefix hash: 5218d31763b785d3f9cb58828e254d40a1f243c8cf67da21e36054b78a28f9f2
Tx public key: de5269e8c1287e3005a6bc825886d8a1053a679f7eddd898c47af42165292c75
Timestamp: 1698216378 Timestamp [UCT]: 2023-10-25 06:46:18 Age [y:d:h:m:s]: 01:088:18:40:47
Block: 877172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324636 RingCT/type: yes/0
Extra: 01de5269e8c1287e3005a6bc825886d8a1053a679f7eddd898c47af42165292c750211000000014b8f5122000000000000000000

1 output(s) for total of 0.761316162000 dcy

stealth address amount amount idx
00: c1ee4f44da4993d76e8fa0559ece144b317b06a108a1df65a84f7053003e4998 0.761316162000 1332534 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": 877182, "vin": [ { "gen": { "height": 877172 } } ], "vout": [ { "amount": 761316162, "target": { "key": "c1ee4f44da4993d76e8fa0559ece144b317b06a108a1df65a84f7053003e4998" } } ], "extra": [ 1, 222, 82, 105, 232, 193, 40, 126, 48, 5, 166, 188, 130, 88, 134, 216, 161, 5, 58, 103, 159, 126, 221, 216, 152, 196, 122, 244, 33, 101, 41, 44, 117, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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