Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68f68c42b0bd89bda34b29d48f22976d28dfb48ded10da9cc8ed93a8db16bb35

Tx prefix hash: df4bf8dca1be512d5823c8bab30c410fdd7f4c6a8c31fda603ecd970d7a6a507
Tx public key: 5db3286d66d14004cb5e940c226f3703abe5e88f1b522b9da650e2578556e19e
Timestamp: 1728610461 Timestamp [UCT]: 2024-10-11 01:34:21 Age [y:d:h:m:s]: 00:206:12:11:03
Block: 1128936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147395 RingCT/type: yes/0
Extra: 015db3286d66d14004cb5e940c226f3703abe5e88f1b522b9da650e2578556e19e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4f2cec84f979efb09430da3b1003604ff3333dcf3be4af75793936ffad60abc 0.600000000000 1611759 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": 1128946, "vin": [ { "gen": { "height": 1128936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4f2cec84f979efb09430da3b1003604ff3333dcf3be4af75793936ffad60abc" } } ], "extra": [ 1, 93, 179, 40, 109, 102, 209, 64, 4, 203, 94, 148, 12, 34, 111, 55, 3, 171, 229, 232, 143, 27, 82, 43, 157, 166, 80, 226, 87, 133, 86, 225, 158, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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