Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca749422d2f12f1df850098a205ba2484a238317e1ccb0313e8ba041c7d76f5d

Tx prefix hash: 9fbd0a92fedb1c076809021d1fa72f727e41975f129a044cc17f6c341b231e4e
Tx public key: 85a83677cf06d02b0eac66270bfc26be99e9c450aebd8170cf08d432e928b3e1
Timestamp: 1706930801 Timestamp [UCT]: 2024-02-03 03:26:41 Age [y:d:h:m:s]: 01:292:06:08:53
Block: 949184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467672 RingCT/type: yes/0
Extra: 0185a83677cf06d02b0eac66270bfc26be99e9c450aebd8170cf08d432e928b3e10211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5407f298b3324ae3fcd7417033f946eabc9069f0a58ddf8d507ca815cdb2e89c 0.600000000000 1407706 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": 949194, "vin": [ { "gen": { "height": 949184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5407f298b3324ae3fcd7417033f946eabc9069f0a58ddf8d507ca815cdb2e89c" } } ], "extra": [ 1, 133, 168, 54, 119, 207, 6, 208, 43, 14, 172, 102, 39, 11, 252, 38, 190, 153, 233, 196, 80, 174, 189, 129, 112, 207, 8, 212, 50, 233, 40, 179, 225, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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