Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b79bf22485f8b5037b78d17c417d3c66b522f19c2cb437a7b10777b39d54c341

Tx prefix hash: b45f75a094aa677401b4a7232c79c8d60e9b39a757e789062a18496cd520c729
Tx public key: b1c28a02a30e758ee5cdf4a59ddd84504545c61a272c06db86e7636293876284
Timestamp: 1725466194 Timestamp [UCT]: 2024-09-04 16:09:54 Age [y:d:h:m:s]: 00:220:06:35:09
Block: 1102875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157273 RingCT/type: yes/0
Extra: 01b1c28a02a30e758ee5cdf4a59ddd84504545c61a272c06db86e7636293876284021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 839d9ab72688f3ca38004725ecd5ec408d8e55f2772d24881a1be65c542eb5d7 0.600000000000 1579480 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": 1102885, "vin": [ { "gen": { "height": 1102875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "839d9ab72688f3ca38004725ecd5ec408d8e55f2772d24881a1be65c542eb5d7" } } ], "extra": [ 1, 177, 194, 138, 2, 163, 14, 117, 142, 229, 205, 244, 165, 157, 221, 132, 80, 69, 69, 198, 26, 39, 44, 6, 219, 134, 231, 99, 98, 147, 135, 98, 132, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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